Why are we doing this?

We’ve been running into a lot of duplicate code in our ElectricalContract system, especially when it comes to checking whether each subsystem or motor is ready. Right now, adding a new motor often requires defining multiple isXXXReady functions across different files, which is repetitive and hard to maintain. This change is intended to better separate year-specific hardware, like the shooter we used this season, from more stable, evergreen components such as cameras and the drive chassis.

Asana task URL:

Whats changing?

• Added Hardware to keep track of all the season-specific hardware.
• Added GeneralContract to initialize all the season-specific hardware.
• Repurposed Contract202x to contain season-specific drive and camera IDs.
• Each contract will now have a set in their constructor to specify which hardware is ready.

Questions/notes for reviewers

• If this gets approved, we should also make similar changes to https://github.com/Team488/FRCRobotTemplate

How this was tested

• tested on robot
• tested in simulator
• unit tests added

Video/screenshots (from simulator or live robot)

PR feedback legend